Fix name resolution in typedef and allow defaults for template tags#45483
Fix name resolution in typedef and allow defaults for template tags#45483
Conversation
80fa780 to
3d9187f
Compare
sandersn
left a comment
There was a problem hiding this comment.
Looks good, one request in the parser and one in the tests.
|
I'm debating whether |
|
@sandersn can you take another look? |
|
@typescript-bot test this |
|
The user suite test run you requested has finished and failed. I've opened a PR with the baseline diff from master. |
|
|
@rbuckton FYI you can run |
|
Heya @andrewbranch, I've started to run the inline community code test suite on this PR at 9131c0c. You can monitor the build here. Update: The results are in! |
|
@andrewbranch |
|
Wasn't aware of the |
|
@DanielRosenwasser: Do we want to discuss the syntax for this in a design meeting, or is this ok to merge? |
|
TODO:
|
|
So the syntax means I can't wait to never get this right. 😂 |
|
Hi @rbuckton , I noticed that none of the files changed in this PR seem to be documentation (HTML/MD). Is that hosted in a different repo? Is there a task / issue to track inclusion of this syntax in the handbook? |
|
Just noting that the new JSDoc reference on the site includes this |
Remove a cryptic piece of code that is no longer needed given the ability to specify default values for template arguments [1] [1] microsoft/TypeScript#45483
Remove a cryptic piece of code that is no longer needed given the ability to specify default values for template arguments [1] [1] microsoft/TypeScript#45483
This adds support for Type Parameter defaults in JavaScript files using the JSDoc
@templatetag. The implementation borrows from the syntax used for parameter defaults in JSDoc (namely[foo=1]):This also fixes a name resolution bug when checking the constraint of a
@templatetag.Fixes #45480
Fixes #45481